Method and system of remote diagnostic, control and information collection using a dynamic linked library of multiple formats and multiple protocols with intelligent protocol processor

ABSTRACT

A method, system and computer program product for (1) collecting information from a remote application unit and/or (2) diagnosing or controlling the remote application unit. By supporting dynamic generation of multiple data formats and/or multiple communication protocols, a computer code device increases the likelihood that a supported format and/or protocol will be either receivable or understandable by a receiver without having to pre-generate the protocol or format processor. By utilizing a shareable computer code device (e.g., a dynamic linked library), a new application can utilize tested, proven code without having to reproduce existing functionality.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of application Ser. No.09/453,935, filed May 17, 2000. The present application is related tothe following U.S. applications and patents: Ser. No. 09/453,934 filed2000-05-17; Ser. No. 09/453,936 filed 2000-05-17; Ser. No. 09/453,937filed 2000-05-17; Ser. No. 09/440,692 filed 1999-11-16; Ser. No.09/440,647 filed 1999-11-16, now U.S. Pat. No. 6,662,225; Ser. No.09/440,646 filed 1999-11-16; Ser. No. 09/440,693 filed 1999-11-16; Ser.No. 09/440,645 filed 1999-11-16; Ser. No. 09/408,443 filed 1999-09-29,now U.S. Pat. No. 6,631,247; Ser. No. 09/407,769 filed 1999-09-29, nowU.S. Pat. No. 6,581,092; Ser. No. 09/393,677 filed 1999-09-10; Ser. No.09/311,148 filed 1999-05-13; Ser. No. 09/192,583 filed 1998-11-17; Ser.No. 09/190,460 filed 1998-11-13, now U.S. Pat. No. 6,208,956; Ser. No.08/883,492 filed 1997-06-26; Ser. No. 09/108,705 filed 1998-07-01; Ser.No. 09/107,989 filed 1998 Jul. 1, now allowed; Ser. No. 08/997,482 filed1997-12-23, now U.S. Pat. No. 6,085,196; Ser. No. 08/997,705 filed1997-12-23, now U.S. Pat. No. 6,279,015; Ser. No. 08/738,659 filed1996-10-30; Ser. No. 08/738,461 filed 1996-10-30; Ser. No. 09/457,669filed 1999-12-09; Ser. No. 08/916,009 filed 1997-08-20, now abandoned;Ser. No. 07/902,462 filed 1992-06-19; Ser. No. 07/549,278 filed1990-07-06; U.S. Pat. Nos. 5,908,493; 5,887,216; 5,818,603; 5,819,110;5,774,678; 5,649,120; 5,568,618; 5,544,289; 5,537,554; and 5,412,779.The contents of each of those applications and patents is incorporatedherein by reference.

BACKGROUND OF THE INVENTION

1. Description of Related Art

With the rise of microprocessor-based appliances and devices, softwaredevelopment has clearly become a significant business. In evaluating andsupporting the appliances and devices, it may be beneficial to monitorexactly how events in the appliance and device occur and how the statesare changing. An example of events is an action caused by userinteraction with an appliance. It may be helpful for a softwaredeveloper to know which commands a user uses most often and how longthose commands take to execute. Such an analysis is often referred to as“profiling.” (Analogous analysis was performed on instructions ininstruction sets to develop reduced instruction set computing (RISC)instructions.)

Further, in designing devices with which a human interacts, it may bedesirable to monitor how the user interacts with such a device. As anexample, it may be desirable to monitor how a user utilizes a controlpanel of an image forming device such as a photocopier, facsimilemachine, printer, scanner, an appliance such as a microwave oven, VCR,digital camera, cellular phone, palm top computer, etc.

Further, it may be desirable to monitor the state of the appliances anddevices to provide diagnostics, services and maintenances. Some eventsmay be caused by the internal changes within the appliances and devices.Some events may be caused by abnormal conditions such as paper jam inthe copiers. Some error conditions and warning conditions may be causedby errors in the software installed in the target appliances anddevices.

Further, users are increasingly utilizing the Internet. There issignificant interest in how users use the Internet, particularly withrespect to how users may use certain web pages. Monitoring a user'susage of the Internet may also become significant.

It may also be desirable to determine how a user is utilizing a certainapplication unit (e.g., a computer running a software application, adevice with an interface to be operated by a user, or a web page). Theuser's usage of the application unit must be monitored and effectivelycommunicated to a remote party.

2. Field of the Invention

This invention generally relates to a method and system that can monitorand communicate events using multiple protocols. Each of the pluralprotocols can be defined through the interface function.

BRIEF SUMMARY OF THE INVENTION

One object of the present invention is to provide a novel and effectivesystem for monitoring events of a target application of an applicationunit.

A further object of the present invention is to provide a system forcommunicating data obtained by monitoring events of a target applicationof an application unit to a remote party.

A further object of the present invention is to provide a system forcommunicating data obtained by monitoring events of a target applicationof an application unit to a remote party allowing various data formatsand communication protocols to facilitate the communication systemconfiguration and received data analysis.

A further object of the present invention is to provide a system forcommunicating data obtained by monitoring events of a target applicationof an application unit to a remote party allowing various data formatsthat ease the analyses of received data at the receiving side.

A further object of the present invention is to efficiently communicatethe monitored event information to a transmission unit.

A further object of the present invention is to efficiently verify thecombination of the two parameters specifying the format and protocol andto meet the restriction requirement on the second parameter.

The present invention achieves these and other objects by monitoring theevents of a target application of an application unit. Monitoringexamples include (1) monitoring a software program being executed on acomputer or workstation under control of a user, (2) monitoring usage ofa control panel of an image forming apparatus (e.g., a copying machine,printer, facsimile, or scanner), an appliance (e.g., a microwave oven,VCR, digital camera, cellular phone, or palm top computer), (3)monitoring any internal state changes such as error conditions andwarning conditions within appliances, devices and any systems andsending the results when requested or when events occur or when presettime interval occurs, (4) externally monitoring states of appliances,devices or system by polling at regular interval, and (5) generallymonitoring any other device or service. The data obtained by monitoringevents of a target application of an application unit, appliance, ordevice can, as a further feature in the present invention, be collected,logged and communicated to a desired location by a store-and-forwardprotocol (e.g., Internet e-mail) or a “direct” connection protocol inwhich a socket connection is made to an ultimate destination machine(e.g., using FTP or HTTP). The use of store-and-forward communicationreduces the costs associated with communicating such data. The data canbe communicated to the desired location at several instances. Suchinstances include each time a user exits a target application, or aftera predetermined number of times that a user has utilized and exited thetarget application of the application unit. If the configuration allowsand if necessary, the direct connection between the monitoredapplication and the monitoring system can be established in addition tothe store-and-forward communication.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the present invention and many of theattendant advantages thereof will be readily obtained as the samebecomes better understood by reference to the following detaileddescription when considered in connection with the accompanyingdrawings, wherein:

FIG. 1 illustrates three networked business office machines connected toa network of computers and databases through the Internet;

FIG. 2 illustrates the components of a digital image forming apparatus;

FIG. 3 illustrates the electronic components of the digital imageforming apparatus illustrated in FIG. 2;

FIG. 4 illustrates details of the multi-port communication interfaceillustrated in FIG. 3;

FIG. 5 illustrates an alternative system configuration in which businessoffice devices are either connected directly to the network or connectedto a computer which is connected to the network;

FIG. 6A illustrates in block diagram format the flow of information toand from an application unit using electronic mail;

FIG. 6B illustrates an alternative way of communicating using electronicmail in which the computer which is connected to the application unitalso serves as a message transfer agent;

FIG. 6C illustrates an alternative way of communicating using electronicmail in which an application unit includes a message transfer agent forexchanging electronic mail;

FIG. 6D illustrates an alternative way of communicating using electronicmail in which a mail server acts as POP 3 server to receive mail for anAppliance/Device and as an SMTP server to send mail forAppliance/Device;

FIG. 7 illustrates an alternative manner of sending messages across theInternet;

FIG. 8 illustrates an exemplary computer which may be connected to thedevice and used to communicate electronic mail messages;

FIG. 9 is a block diagram illustrating connections between a monitoringand logging subsystem, a communications subsystem and a targetapplication of an application unit in the present invention;

FIG. 10 shows a first example of an application unit to which thepresent invention can be applied;

FIG. 11 shows a second example of an application unit to which thepresent invention can be applied;

FIG. 12A shows the general architecture of the system;

FIG. 12B is an exemplary EventData class interface for use in thearchitecture of FIG. 12A;

FIG. 12C is an exemplary FormattedEventData class interface for use inthe architecture of FIG. 12A;

FIG. 13 shows the calling sequence of the interface functions fromapplication software within application unit, appliance or device;

FIG. 14 shows the processing when the Application software instructs DLLto stop monitoring and send the monitored information with the specifiedformat(s) using the specified protocol(s);

FIG. 15 shows the data structure used for intelligent formatting;

FIGS. 16A and 16B shows the source code that implements the processingshown in FIG. 14;

FIG. 17 shows the data structure to handle the intelligent protocolprocessing with caching of the processing function;

FIGS. 18A through 18D show a Processor Builder class according to oneembodiment of the present invention;

FIG. 19 shows the processing when the Application software instructs thesystem to use the specified format and protocol to transmit themonitored data;

FIG. 20 shows the class structure to keep track of the combination offormat and protocols;

FIG. 21 shows the processing of two parameters passed by the Applicationsoftware through the System Manager computer code device;

FIG. 22 shows the processing to get a format parameters and associatedlist of protocols after checking the restriction on the protocol;

FIGS. 23A and 23B are class specification ofCFormatProtocol_InformationBase class that interface with the SystemManager computer code device;

FIGS. 24A and 24B are class specification ofCFormatProtocolCombinationCheck class to verify the combination offormat and protocol; and

FIGS. 25A, 25B and 25C are class specification ofCProtocolRestrictionCheck class where the steps in theoneFormatRestriction function shows the process to modify the mapstructure.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to the drawings, wherein like reference numerals designateidentical or corresponding parts throughout the several views, FIG. 1illustrates (1) various machines and (2) computers for monitoring,diagnosing and controlling the operation of the machines. In FIG. 1,there is a first network 16, such as a Local Area Network (LAN)connected to computer workstations 17, 18, 20 and 22. The workstationscan be any type of computers including IBM Personal Computer compatibledevices, Unix-based computers, or Apple Macintoshes. Also connected tothe network 16 are (1) a digital image forming apparatus 24, (2) afacsimile machine 28, and (3) a printer 32. As would be appreciated byone of ordinary skill in the art, two or more of the components of thedigital image forming apparatus 24 and the facsimile machine 28 can becombined into a unified “image forming apparatus.” The devices 24, 28and 32 and the workstations 17, 18, 20 and 22 are referred to asmachines or monitored devices and other types of devices may be used asthe machines or monitored devices, including any of the devicesdiscussed below. In some configurations, one or more workstations may beconverted to business office appliance. One example of such appliance iseCabinet from Ricoh demonstrated at Fall Comdex in 1999 at Las Vegas.Also, a facsimile server (not illustrated) may be connected to thenetwork 16 and have a telephone, ISDN (Integrated Services DigitalNetwork), cable or wireless connection. In addition to the digital imageforming apparatus 24, facsimile machine 28, and printer 32 beingconnected to the network 16, these devices may also include conventionaltelephone and/or ISDN and/or cable and/or wireless connections 26, 30and 34, respectively. As is explained below, the business officemachines, business devices or business office appliances 24, 28 and 32communicate with a remote monitoring, diagnosis and control station,also referred to as a monitoring device, through the Internet via thenetwork 16 or by a direct telephone, ISDN, wireless, or cableconnection.

In FIG. 1, a wide area network (WAN) (e.g., the Internet or itssuccessor) is generally designated by 10. The WAN 10 can either be aprivate WAN, a public WAN or a hybrid. The WAN 10 includes a pluralityof interconnected computers and routers designated by 12A-12I. Themanner of communicating over a WAN is known through a series of RFCdocuments obtained by HTTP//:www.ietf.org/rfc.html, including RFC 821entitled “Simple Mail Transfer Protocol”; RFC 822 entitled “Standard forthe Format of ARPA Internet Text Message”; RFC 959 entitled “FileTransfer Protocol (FTP)”; RFC 2045 entitled “Multipurpose Internet MailExtensions (MIME) Part One: Format of Internet Message Bodies”; RFC 1894entitled “An Extensible Message Format for Delivery StatusNotifications”; RFC 1939 entitled “Post Office protocol—Version 3”; andRFC 2298 entitled “An Extensible Message Format for Message DispositionNotifications.” The contents of each of those references areincorporated herein by reference.

TCP/IP related communication is described, for example, in the book“TCP/IP Illustrated,” Vol. 1, The Protocols, by W. R. Stevens, fromAddison-Wesley Publishing Company, 1994, which is incorporated herein byreference. Volumes 1-3 of “Internetworking with TCP/IP” by Corner andStevens are also incorporated herein by reference in their entirety.

In FIG. 1, a firewall 50A is connected between the WAN 10 and thenetwork 16. A firewall is a device that allows only authorized computerson one side of the firewall to access a network, computers or individualparts on the other side of the firewall. Firewalls are known andcommercially available devices and/or software (e.g., SunScreen from SunMicrosystems Inc.). Similarly, firewalls 50B and 50C separate the WAN 10from a network 52 and a workstation 42, respectively. Additional detailson firewalls can be found in “Firewalls and Internet Security” by W. R.Cheswick, and S. M. Bellovin, 1994, Addison-Wesley Publishing, and“Building Internet Firewalls” by D. B. Chapman and E. D. Zwicky, 1995,O'Reilly & Associates, Inc. The contents of those references areincorporated herein by reference.

The network 52 is a conventional network and includes a plurality ofworkstations 56, 62, 68 and 74. These workstations may be in differentdepartments (e.g., marketing, manufacturing, design engineering andcustomer service departments) within a single company. In addition tothe workstations connected via the network 52, there is a workstation42, which is not directly connected to the network 52. Information in adatabase stored in a disk 46 may be shared using proper encryption andprotocols over the WAN 10 to the workstations connected directly to thenetwork 52. Also, the workstation 42 includes a direct connection to atelephone line and/or ISDN and/or cable and/or wireless network 44 andthe database in disk 46 may be accessed through the telephone line,ISDN, cable or wirelessly. The cable used by this invention may beimplemented using a cable which typically is used to carry televisionprogramming, a cable which provides for high speed communication ofdigital data typically used with computers or the like, or any otherdesired type of cable.

Information of the business office machines, business devices orbusiness office appliances 24, 28 and 32 may be stored in one or more ofthe databases stored in the disks 46, 54, 58, 64, 70 and 76. Knowndatabases include (1) SQL databases by Microsoft, Oracle and Sybase (2)other relational databases, and (3) non-relational databases (includingobject oriented databases). Each of the customer service, marketing,manufacturing, and engineering departments may have their own databaseor may share one or more databases. Each of the disks used to storedatabases is a non-volatile memory such as a hard disk or optical disk.Alternatively, the databases may be stored in any storage deviceincluding solid state and/or semiconductor memory devices. As anexample, disk 64 contains the marketing database, disk 58 contains themanufacturing database, disk 70 contains the engineering database anddisk 76 contains the customer service database. Alternatively, the disks54 and 46 store one or more of the databases.

In addition to the workstations 56, 62, 68, 74 and 42 being connected tothe WAN, these workstations may also include a connection to a telephoneline, ISDN, cable, or wireless network which provides a secureconnection to the machine being monitored, diagnosed and/or controlledand is used during communication. Additionally, if one communicationmedium is not operating properly, one of the others can be automaticallyused for communication.

A feature of the present invention is the use of a “store-and-forward”mode of communication (e.g., Internet e-mail) or transmission between amachine and a computer for diagnosing and controlling the machine.Alternatively, the message which is transmitted may be implemented usinga mode of communication that makes direct, end-to-end connections (e.g.,using a socket connection to the ultimate destination).

FIG. 2 illustrates the mechanical layout of the digital image formingapparatus 24 illustrated in FIG. 1. In FIG. 2, 101 is a fan for thescanner, 102 is a polygonal mirror used with a laser printer, and 103designates an F lens used to collimate light from a laser (notillustrated). Reference numeral 104 designates a sensor for detectinglight from the scanner. 105 is a lens for focusing light from thescanner onto the sensor 104, and 106 is a quenching lamp used to eraseimages on the photoconductive drum 132. There is a charging corona unit107 and a developing roller 108. Reference numeral 109 designates a lampused to illustrate a document to be scanned and 110, 111 and 112designate mirrors used to reflect light onto the sensor 104. There is adrum mirror 113 used to reflect light to the photoconductive drum 132originating from the polygon mirror 102. Reference numeral 114designates a fan used to cool the charging area of the digital imageforming apparatus, and 115 is a first paper feed roller used for feedingpaper from the first paper cassette 117, and 116 is a manual feed table.Similarly, 118 is a second paper feed roller for the second cassette119. Reference numeral 120 designates a relay roller, 121 is aregistration roller. 122 is an image density sensor and 123 is atransfer/separation corona unit. Reference numeral 124 is a cleaningunit, 125 is a vacuum fan, 126 illustrates a transport belt, 127 is apressure roller, and 128 is an exit roller. Reference numeral 129 is ahot roller used to fix toner onto the paper, 130 is an exhaust fan and131 is the main motor used to drive the digital image forming apparatus.

FIG. 3 illustrates a block diagram of the electronic componentsillustrated in FIG. 2. The CPU 160 is a microprocessor and acts as thesystem controller. Random access memory (RAM) 162 stores dynamicallychanging information including operating parameters of the digital imageforming apparatus. A non-volatile memory (e.g., a read only memory (ROM)164 or a Flash Memory) stores (1) the program code used to run thedigital image forming apparatus and (2) static-state data, describingthe copier (e.g., the model number, serial number of the copier, anddefault parameters.

There is a multi-port network interface 166 which allows the digitalimage forming apparatus to communicate with external devices through atleast one network. Reference number 168 represents a telephone, ISDN, orcable line, and numeral 170 represents another type of network.Additional details of the multi-port network interface are describedwith respect to FIG. 4. An interface controller 172 is used to connectan operation panel 174 to a system bus 186. The operation panel 174includes standard input and output devices found on a digital imageforming apparatus including a copy button, keys to control the operationof the copier such as number of copies, reducement/enlargement,darkness/lightness, etc. Additionally, a liquid crystal display may beincluded within the operation panel 174 to display parameters andmessages of the digital image forming apparatus to a user.

The local connection interface 171 is a connection through local portssuch as RS232, the parallel printer port, USB, and IEEE 1394. FireWire(IEEE 1394) is described in Wickelgren, I., “The Facts About “FireWire”,IEEE Spectrum, April 1997, Vol. 34, Number 4, pp. 19-25, the contents ofwhich are incorporated herein by reference. Preferably, communicationutilizes a “reliable” protocol with error detection and retransmission.

A storage interface 176 connects storage devices to the system bus 186.The storage devices include a flash memory 178 which can be substitutedby a conventional EEPROM and a disk 182. The disk 182 includes a harddisk, optical disk, and/or a floppy disk drive. There is a connection180 connected to the storage interface 176 which allows for additionalmemory devices to be connected to the digital image forming apparatus.The flash memory 178 is used to store semi-static state data whichdescribes parameters of the digital image forming apparatus whichinfrequently change over the life of the copier. Such parameters includethe options and configuration of the digital image forming apparatus. Anoption interface 184 allows additional hardware such as an externalinterface to be connected to the digital image forming apparatus. Aclock/timer 187 is utilized to keep track of both the time and date andalso to measure elapsed time.

On the left side of FIG. 3, the various sections making up the digitalimage forming device are illustrated. Reference numeral 202 designates asorter and contains sensors and actuators used to sort the output of thedigital image forming device. There is a duplexer 200 which allows aduplex operation to be performed by the digital image forming device andincludes conventional sensors and actuators. The digital image formingdevice includes a large capacity tray unit 198 which allows paper traysholding a large number of sheets to be used with the digital imageforming device. The large capacity tray unit 198 includes conventionalsensors and actuators.

A paper feed controller 196 is used to control the operation of feedingpaper into and through the digital image forming device. A scanner 194is used to scan images into the digital image forming device andincludes conventional scanning elements such as a light, mirror, etc.Additionally, scanner sensors are used such as a home position sensor todetermine that the scanner is in the home position, and a lampthermistor is used to ensure proper operation of the scanning lamp.There is a printer/imager 192 which prints the output of the digitalimage forming device and includes a conventional laser printingmechanism, a toner sensor, and an image density sensor. The fuser 190 isused to fuse the toner onto the page using a high temperature roller andincludes an exit sensor, a thermistor to assure that the fuser 190 isnot overheating, and an oil sensor. Additionally, there is an optionalunit interface 188 used to connect to optional elements of the digitalimage forming device such as an automatic document feeder, a differenttype of sorter/collator, or other elements which can be added to thedigital image forming device.

FIG. 4 illustrates details of the multi-port network interface 166. Thedigital image forming device may communicate to external devices througha Token Ring interface 220, a cable modem unit 222 which has a highspeed connection over cable, a conventional telephone interface 224which connects to a telephone line 168A, an ISDN interface 226 whichconnects to an ISDN line 168B, wireless interface 228, and a LANinterface 230 (e.g., Ethernet) which connects to a LAN 170. Otherinterfaces (not shown) include, but are not limited to, DigitalSubscriber Line (DSL) (original DSL, concentric DSL, and asymmetricDSL). A single device which connects to both a Local Area Network and atelephone line is commercially available from Megahertz and is known asthe Ethernet-Modem.

The CPU or other microprocessor or circuitry executes a monitoringprocess to monitor the state of each of the sensors of the digital imageforming device, and a sequencing process is used to execute theinstructions of the code used to control and operate the digital imageforming device. Additionally, there is (1) a central system controlprocess executed to control the overall operation of the digital imageforming device and (2) a communication process used to assure reliablecommunication to external devices connected to the digital image formingdevice. The system control process monitors and controls data storage ina static state memory (e.g., the ROM 164 of FIG. 3), a semi-staticmemory (e.g., the flash memory 178 or disk 182), or the dynamic statememory (e.g., a volatile or non-volatile memory (e.g., the RAM 162 orthe flash memory 178 or disk 182)). Additionally, the static statememory may be a device other than the ROM 164 such as a non-volatilememory including either of the flash memory 178 or disk 182.

The above details have been described with respect to a digital imageforming device but the present invention is equally applicable to otherbusiness office machines or devices such as an analog copier, afacsimile machine, a scanner, a printer, a facsimile server, or otherbusiness office machines and business office appliance, or appliances(e.g., a microwave oven, VCR, digital camera, cellular phone, palm topcomputer). Additionally, the present invention includes other types ofdevices which operate using store-and-forward or direct connection-basedcommunication. Such devices include metering systems (including gas,water, or electricity metering systems), vending machines, or any othermechanical device (e.g., automobiles) that need to be monitored duringoperation or remote diagnosis. In addition to monitoring special purposemachines and computers, the invention can be used to monitor, control,and diagnose a general purpose computer which would be the monitoredand/or controlled device.

FIG. 5 illustrates an alternative system diagram of the invention inwhich different devices and subsystems are connected to the WAN 10.However, there is no requirement to have each of these devices orsubsystems as part of the invention. Each component or subsystemillustrated in FIG. 5 is individually part of the invention. Further,the elements illustrated in FIG. 1 may be connected to the WAN 10 whichis illustrated in FIG. 5. In FIG. 5, there is illustrated a firewall50-1 connected to an intranet 260-1. The service machine 254 connectedto the intranet 260-1 includes therein or has connected thereto data 256which may be stored in a database format. The data 256 includes history,performance, malfunction, and any other information includingstatistical information of the operation or failure or set-up andcomponents or optional equipment of devices which are being monitored.The service machine 254 may be implemented as the device or computerwhich requests the monitored devices to transmit data or which requeststhat remote control and/or diagnostic tests be performed on themonitored devices. The service machine 254 may be implemented as anytype of device and is preferably implemented using a computerized devicesuch as a general purpose computer.

Another sub-system of FIG. 5 includes a firewall 50-2, an intranet260-2, and a printer 262 connected thereto. In this sub-system, thefunctions of sending and receiving electronic messages by the printer262 (and similarly by a copier 286) are performed by (1) circuitry, (2)a microprocessor, or (3) any other type of hardware contained within ormounted to the printer 262 (i.e., without using a separate generalpurpose computer).

An alternate type of sub-system includes the use of an Internet serviceprovider 264 which may be any type of Internet service provider (ISP),including known commercial companies such as America Online, Earthlink,and Niftyserve. In this sub-system, a computer 266 is connected to theISP 264 through a digital or analog modem (e.g., a telephone line modem,a cable modem, modems which use any type of wires such as modems usedover an ISDN (Integrated Services Digital Network) line, ASDL(Asymmetric Digital Subscriber Line), modems which use frame relaycommunication, wireless modems such as a radio frequency modem, a fiberoptic modem, or a device which uses infrared light waves). Further, abusiness office device 268 is connected to the computer 266. As analternative to the business office device 268 (and any other deviceillustrated in FIG. 5), a different type of machine may be monitored orcontrolled such as a digital copier, any type of appliance, securitysystem, or utility meter such as an electrical, water, or gas utilitymeter, or any other device discussed herein.

Also illustrated in FIG. 5 is a firewall 50-3 connected to a network274. The network 274 may be implemented as any type of computer network,(e.g., an Ethernet or token-ring network). Networking software which maybe used to control the network includes any desired networking softwareincluding software commercially available from Novell or Microsoft. Thenetwork 274 may be implemented as an Intranet, if desired. A computer272 connected to the network 274 may be used to obtain information froma business office device 278 and generate reports such as reportsshowing problems which occurred in various machines connected to thenetwork and a monthly usage report of the devices connected to thenetwork 274. In this embodiment, a computer 276 is connected between thebusiness office device 278 and the network 274. This computer receivescommunications from the network and forwards the appropriate commands ordata, or any other information, to the business office device 278.Communication between the business office device 278 and the computer276 may be accomplished using wire-based or wireless methods including,but not limited to radio frequency connections, electrical connectionsand light connections (e.g., an infrared connection, or a fiber opticsconnection). Similarly, each of the various networks and intranetsillustrated in FIG. 5 may be established using any desired mannerincluding through the establishment of wireless networks such as radiofrequency networks. The wireless communication described herein may beestablished using spread spectrum techniques including techniques whichuse a spreading code and frequency hopping techniques such as thefrequency hopping wireless technique which is disclosed in the BluetoothSpecification (available at the world wide web site www.bluetooth.com),which is incorporated herein by reference.

Another sub-system illustrated in FIG. 5 includes a firewall 50-4, anintranet 260-4, a computer 282 connected thereto, a business officeappliance 285 and a copier 286. The computer 282 may be used to generatereports and request diagnostic or control procedures. These diagnosticand control procedures may be performed with respect to the businessoffice appliance 285 and the copier 286 or any of the other devicesillustrated in or used with FIG. 5. While FIG. 5 illustrates a pluralityof firewalls, the firewalls are preferable but optional equipment andtherefore the invention may be operated without the use of firewalls, ifdesired.

FIG. 6A illustrates a Device/Appliance 300 connected to a typical e-mailexchange system which includes components 302, 304, 306, 308, 310, 312,314, 316, and 318 which may be implemented in a conventional manner andare taken from FIG. 28.1 of Stevens, above. A computer 302 interfaceswith any of the application units 300 described herein. While FIG. 6Aillustrates that the Device/Appliance 300 is the sender, the sending andreceiving functions may be reversed in FIG. 6A. Furthermore, if desired,the user may not be needed to interface with the Device/Appliance 300 atall. The computer interface 302 then interacts with a mail agent 304.Popular mail agents for Unix include MH, Berkeley Mail, Elm, and Mush.Mail agents for the Windows family of operating systems includeMicrosoft Outlook and Microsoft Outlook Express. At the request of thecomputer interface 302, the mail agent 304 creates e-mail messages to besent and, if desired, places these messages to be sent in a queue 306.The mail to be sent is forwarded to a Message Transfer Agent (MTA) 308.A common MTA for Unix systems is Sendmail. Typically, the messagetransfer agents 308 and 312 exchange communications using a TCP/IPconnection. Notably, the communication between the message transferagents 308 and 312 may occur over any size network (e.g., WAN or LAN).Further, the message transfer agents 308 and 312 may utilize anycommunication protocol. In the present invention, steps 302 and 304reside in the library to monitor the application unit's usage.

From the message transfer agents 312, e-mail messages are stored in usermailboxes 314 which are transferred to the mail agent 316 and ultimatelytransmitted to the user at a terminal 318 which functions as a receivingterminal.

This “store-and-forward” process avoids the sending mail agent 304 fromhaving to wait until establishment of the direct connection with themail recipient. Because of network delays, the communication could takea substantial amount of time during which the application would beunresponsive. Such an unresponsiveness is generally unacceptable tousers of the application unit. By using e-mail as the store-and-forwardprocess, retransmission attempts after failures occur automatically fora fixed period of time (e.g., three days). In an alternate embodiment,the application can avoid waiting by passing communicating requests toone or more separate threads. Those threads can then controlcommunication with the receiving terminal 318 while the applicationbegins responding to the user interface again. In yet another embodimentin which a user wishes to have communication completed beforecontinuing, direct communication with the receiving terminal is used.Such direct communication can utilize any protocol not blocked by afirewall between the sending and receiving terminals. Examples of suchprotocols include FTP and HTTP.

Public WANs, such as the Internet, are not considered to be secure.Therefore, messages transmitted over the public WANs (and multi-companyprivate WANs) should be encrypted to keep the messages confidential.Encryption mechanisms are known and commercially available which may beused with the present invention. For example, a C library function,crypto, is available from Sun Microsystems for use with the Unixoperating system. Other encryption and decryption software packages areknown and commercially available and may also be used with thisinvention. One such package is PGP Virtual Private Network (VPN)available from Network Associates. Other VPN software is available fromMicrosoft Corporation.

As an alternative to the general structure of FIG. 6A, a single computermay be used which functions as the computer interface 302, the mailagent 304, the mail queue 306 and the message transfer agent 308. Asillustrated in FIG. 6B, the Device/Appliance 300 is connected to acomputer 301 which includes the message transfer agent 308.

A further alternative structure is shown in FIG. 6C in which the messagetransfer agent 308 is formed as part of the Device/Appliance 300.Further, the message transfer agent 308 is connected to the messagetransfer agent 312 by a TCP/IP connection 310. In the embodiment of FIG.6C, the Device/Appliance 300 is directly connected to the TCP/IPconnection 310 and has an e-mail capability. One use of the embodimentof FIG. 6C includes using a facsimile machine with an e-mail capability(defined in RFC 2305 (a simple mode of facsimile using Internet mail))as the Device/Appliance 300.

FIG. 6D shows a system where an appliance or a device does not itselfhave the capability to receive directly e-mail, but uses the POP3protocol to retrieve the received mail from mail server.

FIG. 7 illustrates an alternative implementation of transferring mailand is based on FIG. 28.3 of Stevens. FIG. 7 illustrates an electronicmail system having a relay system at each end. The arrangement of FIG. 7allows one system at an organization to act as a mail hub. In FIG. 7,there are four MTAs connected between the two mail agents 304 and 316.These MTAs include local MTA 322A, relay MTA 328A, relay MTA 328B, andlocal MTA 322D. The most common protocol used for mail messages is SMTP(Simple Mail Transfer Protocol) which may be used with this invention,although any desired mail protocol may be utilized. In FIG. 7, 320designates a sending host which includes the computer interface 302, themail agent 304, and the local MTA 322A. The Device/Appliance 300 isconnected to, or alternatively included within, the sending host 320. Asanother case, the Device/Appliance 300 and host 320 can be in onemachine where the host capability is built into the Device/Appliance300. Other local MTAs 322B, 322C, 322E and 322F may also be included.Mail to be transmitted and received may be queued in a queue of mail306B of the relay MTA 328A. The messages are transferred across theTCP/IP connection 310 (e.g., an Internet connection or a connectionacross any other type of network).

The transmitted messages are received by the relay MTA 328B and ifdesired, stored in a queue of mail 306C. The mail is then forwarded tothe local MTA 322D of a receiving host 342. The mail may be placed inone or more of the user mailboxes 314 and subsequently forwarded to themail agent 316 and finally forwarded to the user at a terminal 318. Ifdesired, the mail may be directly forwarded to the terminal without userinteraction.

The various computers utilized by the present invention, including thecomputers 266 and 276 of FIG. 5, may be implemented as illustrated inFIG. 8. Further, any other computer utilized by this invention may beimplemented in a similar manner to the computer illustrated in FIG. 8,if desired, including the service machine 254, computer 272, andcomputer 282 of FIG. 5. However, not every element illustrated in FIG. 8is required in each of those computers. In FIG. 8, the computer 360includes a CPU 362 which may be implemented as any type of processorincluding commercially available microprocessors from companies such asIntel, AMD, Motorola, Hitachi and NEC. There is a working memory such asa RAM 364, and a wireless interface 366 which communicates with awireless device 368. The communication between the interface 366 anddevice 368 may use any wireless medium (e.g., radio waves or lightwaves). The radio waves maybe implemented using a spread spectrumtechnique such as Code Division Multiple Access (CDA) communication orusing a frequency hopping technique such as that disclosed in theBluetooth specification.

There is a ROM 370 and a flash memory 371, although any other type ofnon-volatile memory (e.g., EPROM, or an EEPROM) may be utilized inaddition to or in place of the flash memory 371. An input controller 372has connected thereto a keyboard 374 and a mouse 376. There is a serialinterface 378 connected to a serial device 380. Additionally, a parallelinterface 382 is connected to a parallel device 384, a universal serialbus interface 386 is connected to a universal serial bus device 388, andalso there is an IEEE 1394 device 400, commonly referred to as a firewire device, connected to an IEEE 1394 interface 398. The variouselements of the computer 360 are connected by a system bus 390. A diskcontroller 396 is connected to a floppy disk drive 394 and a hard diskdrive 392. A communication controller 400 allows the computer 360 tocommunicate with other computers (e.g., by sending e-mail messages) overa telephone line 402 or a network 404. An I/O (Input/Output) controller408 is connected to a printer 410 and a hard disk 412, for example usinga SCSI (Small Computer System Interface) bus. There is also a displaycontroller 416 connected to a CRT (Cathode Ray Tube) 414, although anyother type of display may be used including a liquid crystal display, alight emitting diode display, a plasma display, etc.

One feature in the present invention is to monitor how a user uses atarget application of an application unit. The term application unit inthis instance refers to a system which a user interacts with andcontrols. A “target application” refers to a user controlled system thatcontrols the application unit. For example, an application unit maytypically be a computer and a target application may then be a softwareprogram, e.g. a word processor, running on the computer which a useroperates, for example by moving a pointer on a computer screen and“clicking” on certain command icons to cause the software program toperform certain functions. In this sense, an application unit in thepresent invention can refer to any of workstations 17, 18, 20, 22, 56,62, 68, 74, 42 shown in FIG. 1 running a software program, the computer301 shown in FIG. 6B running a software program, etc. An applicationunit can also refer to an image forming device such as any of thedigital image forming apparatus 24, facsimile machine 28, and printer 32in FIGS. 1 and 2. In this instance, each of these device applicationunits includes a user interface, such as operation panel 174 (see FIG.3), which a user interacts with and utilizes to control the deviceapplication unit. The present invention can monitor a user selectingcontrols on such an operation panel. As a further example, theapplication unit could also be an appliance, such as a microwave oven,with an operation panel. An application unit can also refer to any otherdevice, including software, with which a user interacts, and in thiscase the target application may refer to only one feature of thesoftware which the user interacts with.

One feature of the present invention is to monitor the user's usage ofsuch a target application of an application unit, and to communicatedata of the monitored usage. This data will typically be transmitted bye-mail by the computer interface 302 of FIG. 6A, or the computer 301 ofFIG. 6B or the Device/Appliance 300 of FIG. 6C. This data of a user'susage of a target application of an application unit can then beutilized in many ways, for example in improving software development, inmonitoring usage of a device (e.g., an image forming device),discovering user difficulties with appliances and software, and findingmost frequently used features of application units.

FIG. 9 shows various elements of the present invention. Moreparticularly, FIG. 9 shows an Device/Appliance 300 including targetapplications 510, 512 and 513. The user interface 510 is an interfacefor a user to control the appliance or device. As discussed above, inone common instance, the target appliance 300 may be a software programrunning on one of the workstations 17, 18, 20, 22 (FIG. 1) of thepresent specification. In this instance, the user interface 510 may be adisplay on a monitor of one of these workstations. In such a case, themonitoring system 515 may monitor the user behavior of clicking theselected menu. Another application may be that the appliance 300 is acopier where “application 2” (512) is a sorting of the multiple copies.Both User interface 510 and “Application 2” (512) would send eventmessages to Monitoring System 515 to be logged. The Monitoring System515 is implemented either only in hardware or using a combination ofhardware and software where the combination includes at least onecomputer readable medium. Examples of computer readable media arecompact discs 119, hard disks 112, floppy disks, tape, magneto-opticaldisks, PROMs (EPROM, EEPROM, Flash EPROM), DRAM, SRAM, SDRAM, etc.Stored on any one or on a combination of computer readable media, thepresent invention includes software for controlling both the hardwareand for enabling the system to interact with a human user. Such software(in the form of computer code devices) may include, but is not limitedto, device drivers, operating systems and user applications, such asdevelopment tools. Such computer readable media further includes thecomputer program product of the present invention for monitoring andcontrolling an application unit. The computer code devices of thepresent invention can be any interpreted or executable code mechanism,including but not limited to scripts, interpreters, dynamic linklibraries, classes (e.g., Java or C++), packages (e.g., Java or C++) andcomplete executable programs.

Another illustrative embodiment of FIG. 9 is an office device such as adigital copier where Application 1 (510) is the aforementioned userinterface. Application 2 (512) is the software error tracking system tomonitor the internal error conditions of the software system.Application 3 (513) is the mechanical error tracking system to monitorthe mechanical error condition such as jam and toner out. All of theapplications are using the Monitoring System (515) and Sending Block(520). As a further example, and as noted above, the Device/Appliance300 may be an image forming device such as the digital image formingapparatus 26, facsimile machine 28, or printer 32 also shown in FIG. 1.In this instance, the user interface 510 may take the form of anoperation panel (e.g., operation panel 174 in FIG. 3) with a pluralityof keys and/or a touch screen which a user operates to control the imageforming device. When the Device/Appliance 300 in FIG. 9 is an imageforming device with a user interface 510, the present invention canmonitor the commands that a user selects.

At a designated time, the logged data of the events is then sent to thesending block 520, which then communicates such monitored event data toa designated party. The monitoring and logging DLL 515 can beimplemented in the device including the Device/Appliance 300 or inanother system control element. The protocol processing system can alsobe implemented in the device including the application unit in FIG. 6C,or can also be implemented in the computer 301 in FIG. 6B to which theapplication unit is attached. The present invention can also take theform of computer control codes recorded on a computer readable medium.

One illustrative embodiment of such a user interface 510 used with adigital image forming apparatus 26, facsimile machine 28, or printer 32is shown in FIG. 11. In that embodiment, the present invention monitorseach time a user presses one of the control buttons on the operationpanel and logs the usage data of such a user usage for subsequentcommunication.

As shown in FIG. 11, such an operation panel 700 may include a touchscreen 705 on which various commands may appear which an operator canselect by touching different portions of the touch screen 705. Theoperation panel 700 may also include a 10-key pad 710 and various othercontrol buttons 715. In the case of an image forming device, the controlbuttons 715 may be commands for selecting a paper size, changing amagnification, changing a darkness of a desired image, etc.

When the Device/Appliance 300 in FIG. 9 is an image forming device andthe user interface 510 corresponds to the operation panel 700 as shownin FIG. 11, the present invention can monitor the commands (shown inFIG. 11) that a user selects. The operation panel 700 shown in FIG. 11may, with modifications, also be an operation panel for auser-controlled appliance such as a microwave oven, VCR, digital camera,cellular phone, palm top computer, etc.

FIGS. 10 and 11 show examples of the Device/Appliance 300 and userinterface 510 of FIG. 9 to which the present invention can be applied.As would be readily apparent to those of ordinary skill in the art, thepresent invention is directed to various types of application unitsincluding various types of user interfaces. The present invention isapplicable to any device to be monitored which includes a userinterface.

FIG. 12 shows the general event management architecture of the systemthat can be implemented as any one, or a combination of, a dynamiclinked library (DLL), a script, a Java or C++ class, a C library orroutine, etc. The remainder of this discussion describes theimplementation in terms of a DLL. In general, an application 510communicates through an interface 550. The interface 550 specifies theAPI for the event management architecture (e.g., how information ispassed via a C function call to the object(s) in the System Manager 560with the same names). The System Manager computer code device 560manages the behavior of other computer code devices by using appropriateobjects and their functions. Similarly, the Event Logger 565 records allthe necessary information such as User ID, Application ID, CumulativeSession Number, Start Time, Duration and Sequence of Events with theelapsed times when requested through the system manager 560. The EventLogger supports functions including: initialize( ), storeEvent( ),stopMonitoring( ), and getEventData( ).

The initialize function receives a string parameter for the ApplicationID. The System Manager 560 calls this function when startMonitoring iscalled by an application 510. The function sets the Application ID,takes care of the Cumulative number of usages, reads the clock to storethe start time in order to compute the elapse time and duration, andsets up the user information by examining the registry.

The initialize function receives a string parameter for the ApplicationID. The System Manager 560 calls this function when startMonitoring iscalled by an application 510. The function sets the Application ID,takes care of the Cumulative number of usages, reads the clock to storethe start time in order to compute the elapse time and duration, andsets up the user information by examining the registry.

After the application 510 has completed its usage monitoring, it callsthe stopMonitoring function so that the duration can be computed. Ifmultiple sessions are stored, this function stops the recording of acorresponding session.

After initialization, the storeEvent( ) function can be called with astring parameter for the Event passed by recordEvent. The EventLogger565 stores the event string and the elapsed time from the start time(recorded during the initialize( ) function call).

The EventLogger 565 also provides access to a getEventData function. Ifthe stopMonitoring was not previously called (i.e., the currentsession's duration field is undefined), the monitoring is stopped bycalling the stopMonitoring function. The stopMonitoring functioncomputes the duration of the current session. The getEventData functionreturns an abstract class with the access functions shown in FIG. 12B.The abstract class facilitates extensions for multiple sessions.

The Format And Protocol Information Base System 570 (implemented as anyone or a combination of package, DLL, static library, etc.) stores theformat and protocol information and checks the combination of formatsand protocols to determine the valid combinations. To facilitate thestorage process, the storeFormatAndProtocol function accepts twoparameters (i.e., one for format and one for protocol). The functionchecks to ensure that the parameters are a valid combination.

The component 570 also includes a getFormatAndProtocolVector functionreturns a format and associated vector of protocols. In one embodiment,the function performs error checking. For example, if a protocol allowsonly one format to be sent, then the format should be the last format inthe function call of selectFormatProtocol. The return value is a booleanvalue where true indicates that valid parameters were returned and falseindicates that no more data is available. The return parameters are intand vector of int. The first int refers to the format while the vectorof int refers to the vector of protocols for the format. When there isno selectFormatProtocol function call, the getFormatAndProtocolVectorreturns the default setting. Also would be evident, other collections(e.g., a list template) may be used in place of a vector.

The Data Format Processor 575 is responsible for formatting event datainto a specified format. One exemplary function is the formatEventDatafunction that receives a pointer to the abstract class EventData. Thereturn value is a pointer to the abstract class FormattedEventData.Generally, interface to the FormattedEventData abstract class is definedas in FIG. 12C.

The Protocol Processor 580 is responsible for outputting the formattedevent data through the specified protocol. In one embodiment, theprocessor 580 also encrypts the body of message. To output the data, theprocessFormattedData function is called with an input pointer to theabstract class FormattedEventData. The function returns a boolean valuewhere “true” represents no errors, and “false” represents the existenceof an error while processing the formatted data.

The System 585 supplies important information and persistent informationacross the execution of the DLL. Some of the important information istimer information through the library call. The registry to keep thenecessary information is another important component of the System 585.Many registry entries are set up at installation time. An exemplarystructure for the registry is:

HKEY_LOCAL_MACHINE--SOFTWARE--RicohMonitor--XXX(ApplicationID)

Where XXX represents the Application ID, the following variables areplaced in the registry under XXX tree: CumulativeUsage, UserID, SMTPServer, Recipients, From, FTP Server, FTP User, FTP Password, FTP TargetPath etc. In one embodiment, CummulativeUsage is an integer, and therest of the variables are strings.

FIG. 13 shows an exemplary calling sequence of various computer codedevices according to the present invention. The application softwaresets up the Application ID and starts the monitoring computer codedevice. When the events to be monitored happen, the application sends amessage to the monitoring computer code device with the event name sothat monitoring computer code device will keep track of the name ofevent and the timing. When the application no longer needs to monitorany activities, the application sends a command to select the format andprotocol to be used to send the monitored information. The applicationthen calls the stopMonitoring function, either explicitly or implicitly,as described below. Although FIG. 13 describes sending the monitoredinformation each time an application stops monitoring, in an alternateembodiment, information is sent only upon a secondary event happening(e.g., elapsed time or after a number of events or monitoring sessionshave occurred).

FIG. 14 describes the process of sending the monitored information(e.g., when the monitoring stops as shown in FIG. 13). After thestopMonitoring request has propagated from the Target Application(through the CMonitorSeqApp (in step 1)) to the CMonitorManager (in step2) which passes the request to the EventLogger system (in step 3). TheCMonitorManager coordinates subsequent communication between the othercomputer code devices. The first such communication is in response to agetEventData request made by the CMonitorManager. In step 5,CMonitorManager obtains a format and associated vector of protocols fromCformatAndProtocolInformationBase. Later, step 6, entitled“CreateDataFormatProcessor,” creates the data formatter for the selectedformatting that is used to format the monitored event data in step 7.Step 8 obtains the protocol processor specified by the applicationsoftware before stopping monitoring. Together, steps 6 and 8 show thatthe formatters and protocol processors can be created dynamically (i.e.,only when they are needed). In addition, created protocol processors canbe cached in the CProcessorBuilder.

FIG. 15 shows the map data structure used for creating the DataFormatProcessor. A map includes at least one (key, value) pair. By using a key(corresponding to one of the possible data formats) as an index valueinto the map, the system selects a corresponding pointer to a functionthat creates the data formatter that will transform the monitored eventdata into the specified data format. When the specified format is sentto the ProcessorBuilder in FIG. 14, the corresponding value in the mapfor the format is the function pointer to create the formatter. Thefunction pointed by the pointer is to create the requested dataformatter. Therefore, the formatter itself is not actually created untilthe function pointed to by the pointer is executed. In addition, theclass returned by this function is the abstract class entitled “dataformatter.” Accordingly, the user of the class does not need to know thedetails of the returned formatter, just the abstract class that definesits basic functions.

FIGS. 16A and 16B are exemplary code embodiments corresponding to theFIG. 14. Step 4 in the source code correspond to getting the specifiedformatter (step 6 of the FIG. 14) while step 5 of the source codeformats the data (step 7 of the FIG. 14).

While the above discussion has generally focused on using a singleprotocol and/or a single data format, in an alternate embodiment, thepresent invention utilizes plural protocols and/or plural data formats.Those protocols and formats can include, but are not limited to any ofthe protocols and formats discussed herein. Exemplary formats include,but are not limited to, uncompressed or compressed versions of any oneof: un-delimited text, SGML, XML, HTML, csv format, and binary. Thisenhances the number of possible ways that data can be transferred tosupport the monitoring of the present invention. Accordingly, oneimplementation of the application sends at least one (format, protocol)pair to be used by the computer code device (e.g., DLL). The computercode device checks that each pair is valid before storing it in the datastructure of two maps. For example, if the format specifies the binaryencoding of fixed format, but the protocol is SMTP with the plain textencoding in the mail body, the format and protocol are not a validpair/combination. Before the monitored data are sent out, the computercode device checks if a selected protocol is restricted to support onlyone format. Two maps are used for this purpose. Then, the systemutilizes the specified data format one at a time to generate therequired format and sends out the generated data over all the protocolspecified for this data format.

The present invention is also applicable to implementations where twodifferent kinds of parameters are specified multiple times where thefirst parameter processing is more costly than the second parameterprocessing. In addition, the some second parameter values may berestricted to supporting only one first parameter value that isspecified last. In such a case, the present invention technique can beutilized to process the system efficiently.

FIG. 17 shows the map data structure (using (key, value) pairs) used forcreating and caching the protocol processor. In one embodiment, for agiven formatted event data, multiple protocols may need to send the sameevent data. Likewise, the same protocol may be requested to send thesame data using different data formats. As discussed above, the key ofeach pair specifies a protocol (e.g., SMTP, FTP or HTTP) to be used. Thevalue of the map is itself a second pair (x,y), where x is a pointer tothe protocol processor object, and where y is a pointer to the functionthat creates the protocol processor. This map is initialized to containthe keys and values with the x value being assigned a flag value (e.g.,zero). When a particular protocol is requested, the x valuecorresponding to the specified key is checked. If the x value is zero,the function pointed to by y value is executed. That execution createsthe protocol processor, and the pointer to the created object is storedin the x value. Then, the newly created or subsequently stored pointerto the object is then returned as a pointer to the abstract class. Step6 of FIGS. 16A and 16B (corresponding to step 8 of FIG. 14) illustratesan exemplary code fragment that calls the createProtocolProcessorfunction. The createProtocolProcessor function returns a pointer to theabstract protocol processor object (identified by the return type“CAbsProtocolProcessor *”). Step 7 of FIG. 16B (corresponding to thestep 9 of FIG. 14) shows sending monitored information in a requestedformat.

FIG. 18A shows the function list and the attributes of theCProcessorBuilder Class according to one embodiment of the presentinvention. The public function createDataFormatProcessor receives thespecification for the Data Formatter and returns the pointer to thespecified Data Formatter object in the abstract class type. The publicfunction createProtocolProcessor function receives the specification forthe Protocol Processor and returns the pointer to the specified ProtocolProcessor in the abstract class type. The m_pDataFormatter attribute ofthe class is used to cache the specified data formatter in the class.The other two map attributes show the structure shown in the FIGS. 15and 17. The function definition section shows the steps used by thevarious functions declared in the function list.

FIG. 19 illustrates three exemplary steps that pass the format andprotocol parameters from the Target Application to the Format andProtocol Information Base System to enable plural protocols and/orformats to be used. Similar to transferring a stopMonitoring request inFIG. 14, FIG. 19 shows how a selectFormatProtocol request is passed fromthe Target Application through the CMonitorSeqApp to theCMonitorManager. The CMonitorManager converts the request into astoreFormatAndProtocol request that is passed on to the Format andProtocol Information Base System, thereby storing the format andprotocol information. Although the parameters are illustrated asintegers, any type can be used that uniquely specifies the format andprotocol. As would be evident, the functions can return either nothingor an error code.

FIG. 20 shows relationships of the CFormatProtocolCombinationCheck class610 and the CProtocolRestrictionCheck class 620 used within the FormatAnd Protocol Information Base System. Generally, theCFormatProtocol_InformationBase interface 600 (described in more detailwith reference to FIGS. 23A and 23B) keeps track of the specifiedformats and protocols. That interface 600 uses the (1)CFormatProtocolCombinationCheck class 610 and (2) theCProtocolRestrictionCheck class 620 for (1) verifying requestedcombinations and (2) checking for restrictions on the protocols,respectively.

FIG. 21 describes the process by which the system manager 560 verifieswhether a specified format and protocol combination is valid. AstoreFormatAndProtocol request from the system manager 560 is initiallyhandled by the CFormatProtocol_InformationBase interface 600. Using therelationships illustrated in FIG. 20, that interface 600 converts therequest to an is FormatProtocolCombinationOK request that is sent on tothe CFormatProtocolCombinationCheck class 610. If that class 610 returns“true,” then the combination is valid; otherwise, the class 610 returnsfalse indicating that the combination is invalid. When the combinationis valid, the two values are stored into two different maps specified inthe FIG. 23A.

FIG. 22 describes the process of returning the format and list ofprotocols. In FIG. 22, int and vector are exemplary output parameters,but other implementations may use other containers (e.g., the listtemplate of the standard template library) to facilitate the restrictioncheck. Generally, the system manager 560 sends agetFormatAndProtocolVector request to theCFormatProtocol_InformationBase interface 600. Using the relationshipsillustrated in FIG. 20, that interface 600 converts the request to agetFormatProtocolVectorMapAfterCheckingProtocolRestriction request thatis sent on to the CProtocolRestrictionCheck class 620.

FIG. 23A is an exemplary class definition ofCFormatProtocol_InformationBase interface/class. The functions,storeFormatAndProtocol and getFormatAndProtocolVector, are publicfunctions used by the System Manager 560 computer code device (an objectof CMonitorManager class). Two map structures keep the specified formatsand protocols passed through the function, storeFormatAndProtocol, afterchecking the validity of the combination of the format and the protocolthrough the object, m_FormatProtocolCombinationCheck ofCFormatProtocolCombinationCheck class. The class also contains theobject, m_ProtocolRestrictionCheck of CProtocolRestrictionCheck class.The flag, m_bFirstGetCall is used to call the function in them_ProtocolRestrictionCheck when the function getFormatAndProtocolVectoris called for the first time. The attribute,m_FormatProtocolVectorMaplterator, is used by thegetFormatAndProtocolVector function to iterate over them_FormatProtocolVectorMap. FIG. 23B shows the steps for three mainfunctions in the CFormatProtocol_InformationBase class 600.

FIGS. 24A and 24B show the class definition ofCFormatProtocolCombinationCheck class 610. The main responsibility ofthe class 610 is to check whether a specified format and protocolcombination is valid. The map, m_CombinationMartix, contains theinformation of the valid combination that is initialized by the functioninitMatrix.

FIGS. 25A, 25B, and 25C show the class definition of theCProtocolRestrictionCheck class 620. The m_bOneFormatRestrictionattribute specifies whether the information is restricted to a singleformat. Other types of restrictions could be implemented by adding otherprivate functions and attributes. An exemplary restriction algorithm forthe present invention is illustrated in FIGS. 25B and 25C (showing thesteps in the private function oneFormatRestriction).

Obviously, numerous modifications and variations of the presentinvention are possible in light of the above teachings. It is thereforeto be understood that, within the scope of the appended claims, theinvention may be practiced otherwise than as specifically describedherein.

1. A method of a monitoring system for monitoring events of a targetapplication in a device, the method comprising: monitoring, by themonitoring system of the device, data of the events sent by the targetapplication based on a monitoring command received from the targetapplication; generating, by the monitoring system, a log of themonitored data; selecting a first protocol from plural Internetapplication layer protocols to transfer the log of the monitored data bya communication unit based on a protocol selection command received fromthe target application; and transferring the log of the monitored databetween a remote receiver and the communication unit through the firstprotocol; and wherein the monitoring, generating, selecting andtransferring steps are initiated internal to the device.
 2. A method ofmonitoring events of a target application in a device according to claim1, wherein the target application is a software program being executedunder control of a user.
 3. A method of monitoring events of a targetapplication in a device according to claim 1, wherein the targetapplication controls an operation panel.
 4. A method of monitoringevents of a target application in a device according to claim 1, whereinthe target application monitors an internal state change.
 5. A method ofmonitoring events of a target application in a device according to claim1, wherein the device is an image forming device.
 6. A method ofmonitoring events of a target application in a device according to claim1, wherein the device is an appliance.
 7. A method of monitoring eventsof a target application in a device according to claim 5, wherein theimage forming device comprises at least one of a copying machine,printer, facsimile or scanner.
 8. A method of monitoring events of atarget application in a device according to claim 1, wherein the firstprotocol comprises at least one of SMTP, FTP and HTTP.
 9. A method ofmonitoring events of a target application in a device according to claim6, wherein the appliance comprises at least one of a microwave oven,VCR, digital camera, cellular phone, image output device and palm topcomputer.
 10. An image output device, comprising: a target applicationconfigured to send events of the target application to a monitoringsystem; and the monitoring system including a processor configured tomonitor data of the events sent by the target application based on amonitoring command received from the target application, to generate alog of the monitored data, to select a first protocol from pluralInternet application layer protocols to transfer the log of themonitored data by a communication unit based on a protocol selectioncommand received from the target application, and to transfer the log ofthe monitored data between a remote receiver and the communication unitthrough the first protocol.
 11. A method of monitoring events of atarget application in a device according to claim 1, wherein themonitoring step comprises monitoring the data of the events sent by thetarget application through an interface communicatively coupled betweenthe target application and the monitoring system.
 12. An image outputdevice according to claim 10, wherein the target application isconfigured to send the events of the target application to themonitoring system through an interface communicatively coupled betweenthe target application and the monitoring system.